Method and system for call administration

ABSTRACT

A call administration service for processing incoming calls during service activation times. One embodiment permits a subscriber to provision the administration service using configuration files, which provide the capability to establish flexible scenarios for the allowance, denial and routing of incoming calls. The present invention automatically routes authorized incoming calls, and permits unauthorized incoming calls to be routed in accordance with a caller&#39;s interactive responses. An embodiment provides multiple methods for interacting with the system, including file and speech input of subscriber provisioning information, and speech input of caller interactive responses.

CROSS-REFERENCES TO RELATED APPLICATIONS

United States Utility Patent Application by M. A. Griffiths, filed onthe same date as this application and entitled “Method and System forImplementing a Call Administration Service for a Public SwitchedTelephone Network”, is hereby incorporated by reference.

FIELD OF INVENTION

The present invention relates generally to the field of communications.More particularly, the present invention relates to a system and methodfor implementing a call administration service.

BACKGROUND

There are many reasons for which a subscriber may want to prevent allcalls to his telephone. For instance: the baby may be sleeping; a familymember may be sick and resting; the subscriber has just returned homeafter working the night shift and wants to sleep; or, perhaps thewireless subscriber is about to enter the library or attend an importantmeeting at which the company CEO is the featured speaker. In each ofthese scenarios the ringing of the telephone is bothersome.

There are also situations in which a subscriber may want to deny callsfrom only certain types of callers. Such callers may includetelemarketers and unknown callers. Additionally, a subscriber may wantto keep the line available for a particular caller, like a son ordaughter who is out later than expected. Furthermore, a wirelesscustomer may desire to deny calls from out-of-area callers to avoidpaying long-distance charges.

For many of the preceding scenarios, a common solution is to unplug thephone. Cutting off all communications is obviously not an optimalsolution. First, the subscriber could not be reached in case ofemergency. Additionally, the subscriber may have wanted to talk to someof those who attempted to call, but could not get through. Moreover,sometimes the subscriber remembers to plug the phone back in only afterrealizing why the subscriber has not received any calls for some time.

Automated techniques were established to overcome these problems and toaddress other scenarios, but they have various disadvantages. Thesetechniques include Caller ID™, Caller ID Plus, Call Block, and SelectiveCall Block.

Caller ID™ and Caller ID Plus are often used by subscribers to screencalls. An incoming caller's number is displayed on the screen of aCaller ID™ device attached to the subscriber's telephone line. Thesubscriber can then chose to answer the phone or not. However, a callercan prevent or “block” the caller's number from displaying on the CallerID™ device. With Caller ID Plus, the caller is forced to unblock thecaller's number or the caller will not be connected to the subscriber'stelephone.

One problem with using both Caller ID™ and Caller ID Plus in this manneris that the phone still rings. Another is that in many instances acaller's number will not display, such as when the call has been placedfrom out of the area or when the caller has blocked his telephone numberfrom being displayed (and the subscriber has Caller ID™ rather thanCaller ID Plus). In these cases, the subscriber must still answer thephone or let it ring until the caller hangs up.

Call Block is a service addressed in U.S. Pat. No. 5,060,255, issuedOctober 1991 to Brown. Brown states in column 2 lines 62-65 that this“service and system arrangement will permit a customer to program aperiod of time where all incoming calls will be routed to anannouncement.” However, one problem with Call Block is that it simplyblocks all calls. There is no capability for keeping the line availablefor access by certain callers, while blocking others.

U.S. Pat. No. 5,467,388, issued November 1995 to Redd, Jr. et al.(hereinafter Redd) addressed some of the shortcomings of Brown. Redddescribes a “system for allowing a telephone subscriber to selectivelyblock incoming calls for selected time periods,” as stated in theabstract.

Additionally, Redd permits the automatic connection of an authorizedcaller as discussed in column 15 lines 55-60 which states that “from acaller's AIN or Caller ID™ number, the Integrated Service Control Pointmay determine whether the caller's number is on an authorized tierlevel. If the number is authorized, the call is terminated (i.e.,connected) to the subscriber.”

Furthermore, as stated in column 12 lines 39-41, Redd employs aprogramming method in which “DTMF is used, and hence the subscriber musthave access to a Touch-Toner™ telephone.” And, a DTMF entry method isdescribed in column 12 lines 43-46 such that “the subscriber may selectfrom a menu of items offering options how to program the service.”

Although addressing some of the limitations of the “all or none”approach of Brown, Redd has several inadequacies. First of all, Redddoes not provide for the flexibility of programming aperiodic activationperiods. Additionally, Redd does not provide a capability to connect thecaller to a device other than the subscriber's telephone. Furthermore,Redd's menu-driven, DTMF programming method is cumbersome, inflexible,and is limited to data entry via a Touch-Tone™ telephone.

U.S. Pat. No. 5,917,817, issued June 1999 to Dunn et al (hereinafterDunn) addressed one shortcoming of Redd, i.e., that of DTMF programming.Dunn describes in column 5 lines 41-44 a system for programming userservices “wherein a web server utilizes a database containing a formsbased program to conduct its communications relative to browsers oncustomer computers.” Dunn, however, requires a separate connection aboveand beyond the user's phone for programming of the user's services. Acomputer with a browser is also required.

What is needed is a call administration system that overcomes theshortcomings of conventional systems while providing additionaladvantages, such as flexibility.

SUMMARY

An embodiment of the present invention implements a call administrationservice, permitting both interactive and automatic denial and routing ofcalls, under the direction of subscriber provisioning. Embodiments ofthe present invention operate in a public switched telephone networkenvironment, a cellular network environment, and other environments.Embodiments of the methods set forth herein are applicable to anycommunications environment in which a called party, subscriber, or otherparty desires to control the calls or communications sent to a calledparty.

An embodiment of the present invention provides for the provisioning andactivating of a call administration service. Processing of an incomingcall during 30 activation occurs in accordance with the subscriberprovisioning. An incoming call is detected and a caller identificationis extracted from the received incoming call information. Routing isperformed according to the subscriber-provisioning information, androuting may take place interactively, requiring caller input, orautomatically without I caller input. An embodiment of automatic routingcomprises receiving an access table, validating that the calleridentification exists within the access table and receiving an at leastone primary auto-route option associated with the validated calleridentification. The incoming call is then connected to an at least onesubsystem identified by the at least one primary auto-route option.Subsystems comprise service provider systems (such as voice mailsubsystems) and end user “systems” (such as home phones, cellularphones, BLUETOOTH communication devices, and PBXs).

Another embodiment of the present invention provides for alternateprovisioning mechanisms for receiving and storing of subscriberprovisioning information. Such alternate provisioning interfacemechanisms comprise a DTMF menu, voice processing, speech processing,use of a browser form, and use of a formatted file translationmechanism. Voice and speech processing differ in that voice processingis specific to the speaker, whereas speech processing recognizes spokenwords and is indifferent as to the actual speaker. Formatted filetranslation comprises reading a file, extracting certain data fields,and translating that data into a current configuration or storing thatdata in an at least one configuration file.

One embodiment of the present invention implements a browser form on aclient device. Another embodiment comprises a cell phone as the clientdevice.

The present invention includes an embodiment which provides foractivation and configuration via a command, a script, a configurationfile name or a pipeline with an optional at least one invocation (orstarting) point and an optional at least one termination (or ending)point. An embodiment of a command comprises a single instruction. Anembodiment of a script comprises multiple commands executedsequentially. An embodiment of a configuration file comprises a filecomprising commands, scripts, other configuration files, invocation andtermination points, and other configuration (or subscriber provisioning)information, such as access files (or access tables), journalingoptions, bypass options, and periodic/aperiodic activation dates andtimes. A pipeline is to a configuration file what a script is to acommand. In other words, a pipeline comprises multiple configurationfiles executed sequentially. An embodiment of a pipeline comprises astring of names of configuration files on a command line. An alternativeembodiment of a pipeline comprises a file containing the names ofmultiple configuration files to be sequentially executed.

An embodiment of the present invention features interactive routing,which comprises announcing to the caller, inter alia, that the calladministration system is active, receiving optional input from thecaller, and routing the incoming call in accordance with the caller'soptional input. Routing may terminate (or connect) the incoming call tothe subscriber or a subscription (i.e., subscriber) subsystem, such as avoice mail subsystem (VMS). Routing also includes disconnecting theincoming call.

A further embodiment includes an optional caller input comprising atleast one of a bypass code, a bypass route option, and an unauthorizedcaller route option. Entry of a valid bypass code results in theconnection of the incoming call to the subscriber. Entry of a validbypass code followed by the entry of a bypass route option as menuresponses results in the connection of the incoming call to thesubscription subsystem associated with the bypass route option. And,entry of an unauthorized caller route option as a menu selection resultsin the connection of the incoming call to the subscription subsystemassociated with the unauthorized caller route option. Note that an“unauthorized caller” comprises a caller whose call identification(comprising a name or a number) is not in the current access list.Unauthorized caller route options are provisioned by the subscriber.

Another embodiment implements the bypass code as a spoken bypass code.This embodiment employs off the shelf voice or speech recognitionsoftware to establish the validity of the spoken bypass code. Aspreviously stated, voice recognition is specific to the speaker, whilespeech recognition recognizes words spoken regardless of the speaker.

Yet another embodiment comprises at least two auto-route options asbeing associated with the authorized caller identification in the accesslist (or access table). Allowing at least two auto-route options permitsan incoming call (associated with the authorized caller identification)to be routed in a multicast fashion. In this way a conference, such asan audio or video conference, can be established by the calladministration service.

An embodiment of the present invention comprises at least one secondaryauto-route option for fail safe operations. Should the subscriptionsubsystem associated with the at least one primary auto-route option beunavailable, then the secondary auto-route option permits the incomingcall to be routed to a backup subscription subsystem.

Embodiments of the present invention permit the subscriber to set up awide range of configuration scenarios. The subscriber provisioninginformation that can be instantiated comprises service activation times,bypass codes, authorized access numbers, authorized access names,routing options, journaling options, command entries, script entries,configuration file name entries, pipeline entries, directory entries,and priority options. Directory entries allow for the organizing ofpersistent files (configuration file entries, pipeline entries, accesslist files, bypass code files, journaling option files, etc.).

The present invention is extremely flexible in both provisioning andoperational aspects. For instance there are multiple ways for a user toprovision the call administration service. Not only is DMTF inputavailable for simple provisioning tasks, but also several other methodsexist. These include: voice input; a thin client, browser-based inputvia a cellular telephone; email of formatted files; and automatedscanning of formatted files.

Additionally, persistent configuration files provide a significant levelof flexibility beyond that of conventional systems. The subscriber canset up and store multiple scenarios in advance and have the presentinvention invoke a configuration file when needed. For instance, a monthof July configuration file could be set up, saved, and later invoked bythe system to program the service for operation during the entire monthof July. Instructions may then be carried out for: (1) the subscriber'ssummer vacation week; (2) the subscriber's summer school mid-tern examstudy nights; (3) the night of the Major League Baseball All Star Game;and (4) the Fourth of July holiday. In addition, the subscriber couldhave a “No Calls for the Rest of the Night” file stored on the system sothat the subscriber could quickly set up this “no calls” scenariomanually by merely telling the present invention to invoke thatconfiguration file immediately—rather than go through the motions ofentering the data to set up such a scenario each time it is needed.

Another benefit of persistent configuration files is that default filesmay be offered by the service provider in order to help a new subscriberget up and running. Configuration files may also be exchanged amongsubscribers so that more sophisticated users of the call administrationservice can help novice subscribers enjoy the full benefits of the calladministration service's flexibility.

Another aspect of an embodiment of the present invention that accountsfor the flexibility of the present invention is the availability ofaperiodic system activation times, in addition to periodic times andsingle events. For example, “activate on this Monday from 7-11 AM, thenFriday from 4-8 PM, and finally next Monday from 6-10 PM” can easily beprogrammed into a configuration file, rather than requiring a user toremember to set up these activation times separately.

From an operational standpoint, automatic routing of authorized callers(i.e., those callers whose numbers are in the access table) is alsoextremely flexible. If a caller's number (or other identification, suchas the caller's name) is in an access table that is active for thecurrent system configuration, then a subscriber has the option ofconnecting that caller to any valid subsystem including the subscriber'shome phone. Other subsystems would include a cell phone, pager or abusiness voice mail system, in order to ensure that a salesman, forexample, does not miss an expected call from a client. Multicasting isalso available by specifying multiple routes in an access table.Multicasting is used to establish conference calls or video conferences(depending upon the source incoming call).

As a fail safe procedure, secondary routes may also be provisioned. Ifthe primary system is unavailable, then a secondary route provides thesubscriber with a backup subsystem for connecting the caller. In thisway, the subscriber is less likely to miss a call altogether.

Also from an operational standpoint, interactive routing is available.In one embodiment, interactive routing allows a caller to state a bypasscode to connect the incoming call to a subscriber subsystem. In thepreferred embodiment, that subsystem is the subscriber's phone (home orcell phone), but another embodiment would permit a caller to select asubscriber subsystem with which to connect (and the available subsystemchoices can be provisioned by the subscriber).

Another advantage of an embodiment of the present invention is theavailability of a journaling feature. A subscriber has the option ofenabling journaling to log the disposition of calls during the calladministration activation period. Additionally, the information logged(such as caller name, caller number, date-time stamp, call disposition,etc.) is a configurable parameter. Using the journaling feature allowsthe subscriber to determine who called during the call administrationactivation period and where the call was routed.

An additional advantage provided by an embodiment of the presentinvention concerns cost control in the cellular environment. By way ofexample, when a salesperson leaves the local calling area, thesalesperson may want to limit the calls that can be received on thatsalesperson's cellular phone to the most important calls, and redirectless important calls to a VMS. In this manner, the salesperson incurslong distance charges only for those calls that are of immediate concernor of a high priority.

Additional objects, advantages, and novel features of the invention willbe set for the in part in the description which follows, and in partwill become more apparent to those skilled in the art upon examinationof the following, or may be learned by practice of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 comprises an embodiment of the present invention in a wirelessnetwork environment.

FIG. 2 comprises an overall flow diagram of an embodiment of the presentinvention in a wireless network environment.

FIG. 3 comprises a flow chart of the automatic routing feature of anembodiment of the present invention in a wireless network environment.

FIG. 4 comprises a flow chart of the interactive routing feature of anembodiment of the present invention in a wireless network environment.

FIG. 5 comprises an exemplary illustration of using a thin clientbrowser on a cellular telephone for provisioning of the presentinvention.

FIG. 6 comprises an exemplary illustration of using a thin clientbrowser on a cellular telephone to fill out a form for the provisioningof the present invention.

FIG. 7 comprises an exemplary configuration file and pipeline forflexible provisioning of the present invention.

FIG. 8 comprises a flow chart of exemplaryactivation/deactivation/provisioning processes for an embodiment of thepresent invention.

FIG. 9 comprises an embodiment of the present invention in a PublicSwitched Telephone Network environment.

FIG. 10 comprises an overall flow diagram of an embodiment of thepresent invention in a public switched telephone network environment.

FIG. 11 comprises a flow chart of the automatic routing feature of anembodiment of the present invention in a public switched telephonenetwork environment.

FIG. 12 comprises a flow chart of the interactive routing feature of anembodiment of the present invention in a public switched telephonenetwork environment.

DETAILED DESCRIPTION

In the following discussion of embodiments of the present invention,numerous specific details are set forth in order to provide a thoroughunderstanding of the present invention. The present invention may bepracticed without some or all of these specific details. In otherinstances, well known process operations have not been described indetail in order not to unnecessarily obscure the present invention.

FIG. 1 comprises an embodiment of the present invention in a wirelessnetwork environment. Referring now to FIG. 1, a cellular network isshown. The cellular network comprises at least one Mobile SwitchingCenter (MSC) 200, which interfaces to the Public Switched TelephoneNetwork (PSTN) 10 via an Access Tandem (AT) switch 70. The PSTN 10 willbe discussed in detail in FIG. 9. The MSC 200 manages many cell sites,each of which contains a base station and antenna 210. The MSC 200 mustalso be able to locate a stationary cell phone 220 and a mobile cellphone 230 (mobile because the user is in a car, for instance). Largecellular networks are comprised of multiple MSCs 200.

At the MSC facility 200, the MSC 200 interfaces with the Home LocationRegister (HLR) 240, the Visitor Location Register (VLR) 250, and OtherDatabases 260, such as an Authentication Center (AC) and an EquipmentIdentification Register (EIR), via an SS7 network 270. The HLR 240contains location and service information about the subscriber. The VLR250 contains roaming information about visiting cellular phones thathave registered in the local area. The AC authenticates calls, while theEIR contains a list of illegal numbers, stolen phones and faultyequipment.

In one embodiment, the MSC 200 implements the call administrationservice (CAS) methods. In another embodiment, a CAS processor 290implements the call administration service methods. CAS storage database280 is utilized in another embodiment for storing subscriberprovisioning information, comprising service activation times(comprising at least one of invocation points and termination points),bypass codes, authorized caller identification comprising authorizedaccess numbers and authorized access names, routing options, journalingoptions, activators (comprising at least one of command entries, scriptentries, configuration file name entries, and pipeline entries),directory entries, and priority options. Note that activation timescomprise at least one of a single event (i.e., Tuesday from 8 AM to 5PM), a periodic event (i.e., every Tuesday from 8 AM to 5 PM), and anaperiodic event (i.e., Tuesday from 8 AM to 5 PM, Wednesday from 7 AM to9 AM, and Friday from 11 AM to 1 PM).

When a caller using telephone 131 places a call to a subscriber using acellular phone 220, an SSP 30 sends an AIN (Advanced IntelligentNetwork) query to SCP 90 via an SS7 Network 20. SCP 90 then communicateswith HLR 240 via SS7 Networks 20 and 270. HLR 240 stores informationabout the subscriber, such as the subscriber's location. Once thesubscriber is located, HLR 240 responds to the SCP 90, which sends theappropriate SSP 30 the information necessary to connect the caller tothe subscriber's cellular phone 220. The incoming call is routed fromthe SSP 30, which is connected to the caller's end office 120, throughthe PSTN 10 to the MSC 200. The MSC 200 locates the cellularsubscriber's cellular phone 220 using information obtained from the HLR240 and routes the incoming call to the appropriate base station 210.The base station 210 converts the landline signal of the incoming callto a cellular signal, and transmits the incoming call to thesubscriber's cellular phone 220.

In one embodiment of the present invention, the subscriber activates thecall administration service by sending an activator to the CAS processor290. An activator, in one embodiment, comprises a feature code, such as*88, which is entered via a DTMF data entry interface to the CASprocessor 290. After receiving the activator, the CAS processor 290 thensets an activation status flag.

Once the call administration service is activated, the CAS processor 290routes an incoming call in accordance with subscriber provisioninginformation. For instance, if the caller using telephone 131 is anauthorized caller (i.e., the caller's number for telephone 131 appearsin subscriber provisioning information comprising an access table), thenthe CAS processor 290 receives incoming call information from the SCP 90by way of the HLR 240 and extracts the caller number from the incomingcall information. CAS processor 290 then compares the extracted callernumber to the caller numbers in the access table. If a match is found,the CAS processor 290 next extracts a primary auto-route numberassociated with the caller number in the access table.

CAS processor 290 uses the primary auto-route number to look up anaddress in the CAS storage 280 for a subsystem associated with theprimary auto-route number. If the auto-route number is associated withthe subscriber's cell phone 220, then the CAS processor 290 sends aconnect message via the HLR 240 to the MSC 200 requesting the connectionof the incoming call to the subscriber's cellular phone 220.

FIG. 2 comprises an overall flow diagram of an embodiment of a method ofthe present invention in a wireless network environment. In oneembodiment, the CAS processor 290 starts the call administration serviceroutine in step 300 when the subscriber is added to a list of calladministration service subscribers by the service provider. Thesubscriber provisions the call administration service in step 303 byestablishing a data entry interface to the CAS processor 290.

Provisioning, in the embodiment shown in FIG. 2, comprises the processof data entry by a subscriber using a data entry interface to the CASprocessor 290 to configure the call administration system. An embodimentof the present invention provides a DTMF (Dual Tone Multiple Frequency)menu response system to provision the call administration service.Alternate embodiments provide for voice processing and speech processingdata entry using commercial off the shelf software, a browser form ofdata entry and a formatted file translation data entry mechanism. Thebrowser form of data entry may be implemented on a thin client device ora cellular phone in alternate embodiments. After receiving provisioninginformation from the subscriber in step 303 via a provisioning dataentry interface, CAS processor 290 then stores the provisioninginformation in CAS storage database 280. CAS storage database 280comprises secondary storage for persistent subscriber provisioninginformation.

The CAS processor 290 activates the call administration service in step306. In one embodiment of the present invention, the CAS processor 290receives a system activator from the subscriber provisioninginformation. The system activator comprises at least one of a command, ascript, a configuration file name and a pipeline. The CAS processor 290receives from the subscriber provisioning information an activation timecomprising at least one of an invocation point (or start time and/ordate) and a termination point (or ending time and/or date). The CASprocessor 290, using an activation setter, sets an activation flag orsemaphore during periods of service activation.

In step 310, CAS processor 290 receives subscriber provisioninginformation from CAS storage database 280. Alternatively, the subscriberprovisioning information is set directly by the subscriber via aprovisioning data interface to the CAS processor 290 as the currentconfiguration. This particular provisioning data interface gives thesubscriber the option of storing subscriber-entered provisioninginformation, setting the subscriber-entered provisioning information asthe current configuration, or simultaneously storing and setting (as thecurrent configuration) the subscriber-entered provisioning information.

Next, in step 315, the CAS processor 290 receives incoming callinformation, comprising a caller identification, such as a caller numberor caller name. The incoming call information is extracted from the TCAPinformation by the CAS processor 290.

In step 320, the CAS processor 290 determines if the subscriber hasactivated the call administration service. An embodiment implements thisstep by checking a flag or semaphore which indicates the calladministration service activation status. If the system has not beenactivated, then in step 330 the incoming call is connected to thesubscriber.

If the call administration service is active, then in step 340, the CASprocessor 290 searches the current access table for a calleridentification, such as a caller number. In another embodiment, a calleridentification comprises a caller name. If the caller identification isnot found within the current access table, then the CAS processor 290performs interactive routing at step 350. Interactive routing isdiscussed in further detail starting at step 500 in FIG. 4. Otherwise,if the caller identification is found in the current access table theCAS processor 290 performs automatic routing at step 360. Automaticrouting is discussed in further detail starting at step 400 in FIG. 3.

FIG. 3 comprises a flow chart of the automatic routing feature of anembodiment of the present invention in a wireless environment. The CASprocessor 290 starts the automatic routing methods at step 400. In step410, the CAS processor 290 receives auto-routing options from thesubscriber provisioning information (i.e., from an access table, in oneembodiment).

At step 420, the CAS processor 290 checks the (currently active) accesstable to I determine if one primary auto-route number is associated withthe authorized caller. If exactly one primary auto-route numberassociated with the authorized caller exists, then the CAS processor 290connects the incoming call to that primary auto-route subsystemrepresented by the primary auto-route number. In one embodiment, if theprimary auto route number is “0”, then the incoming call is connected tothe subscriber's home phone Note that subsystems comprise serviceprovider systems (such as voice mail subsystems) I 5 and end user“systems” (such as home phones, cellular phones, BLUETOOTH communicationdevices, and PBXs). If CAS processor 290 at step 420 determines thatthere is not exactly one primary auto-route number associated with theauthorized caller, then at step 440 the CAS processor 290 determineswhether there is more than one primary auto-route number in I 10 theaccess table. If more than one primary auto-route number exists in theaccess table, then the CAS processor 290 connects the incoming call toeach subsystem (specified by a primary auto-route number) in a multicastfashion. In this manner, a video or audio conference may be established.

If CAS processor 290 at step 420 determines that there is not exactlyone primary auto-route number associated with the authorized caller,then at step 440 the CAS processor 290 determines whether there is morethan one primary auto-route number in the access table. If more than oneprimary auto-route number exists in the access table, then the CASprocessor 290 connects the incoming call to each subsystem (specified bya primary auto-route number) in a multicast fashion. In this manner, avideo or audio conference may be established.

At step 465, the CAS processor 290 checks the (currently active) accesstable to determine if a secondary auto-route number associated with anauthorized caller exists within the access table. The CAS processor 290executes step 465 if, after executing steps 420 and 440, the CASprocessor 290 has determined that no primary auto-routes were specifiedin the access table (i.e., if one or more primary auto-routes were notspecified, then no auto-routes were specified).

Note that in one embodiment, the CAS processor 290 determines whethersubsystems are available. Routing of an incoming call takes place onlyif a subsystem is (or subsystems are) available. A subsystem isavailable if an incoming call can be connected to or terminated at thesubsystem. Exemplary reasons a subsystem may be unavailable orunreachable include i) called party does not subscribe to a serviceimplemented by that subsystem (i.e., VMS), ii) communications path isdown, and iii) device (i.e., phone) is “off hook”. CAS processor 290determines that a called party does not subscribe to a service byquerying a subscriber service database. CAS processor 290 determinesthat a communications path is down or that a device is off hook uponreceipt of an appropriate TCAP message.

If a secondary auto-route number exists in the (currently active) accesstable, as determined by the CAS processor 290 in step 465, then in step475 the CAS processor 290 routes the incoming call to that secondarysubsystem. In this manner, a fail safe routing mechanism is provided toroute to a backup subsystem.

After the CAS processor 290 has routed an incoming call according tostep 430, 450, or 475, or the CAS processor 290 has not connected anincoming call after executing step 465, the CAS processor 290 thendetermines whether the subscriber has requested journaling in step 480by reading a journaling status flag. Journaling is the logging ofinformation about an incoming call. Logged information comprises atleast one of a caller name, a caller number, a date/time stamp and theincoming call disposition (i.e., connected to subscriber, multicast,connected to a primary auto-route number subsystem, etc.). If thesubscriber has requested journaling, then the requested journalinginformation is stored at step 485 in CAS storage database 280.

In one embodiment, stored journaling information may be formatted andviewed via a graphical user interface (GUI). Formatting includes HTMLformatting. A subscriber may then subsequently view the HTML-formattedjournaling information using a browser on a thin or thick client. Inanother embodiment, stored journaling information may be transferredelectronically to another database for follow-on processing by a systemsuch as the Personal Call Manager.

The Personal Call Manager comprises computer programs, computer systems,and telephone systems that allow a customer (i.e., a subscriber) toretrieve real-time and historical information concerning the customer'suse of a telecommunications system. This information is known as a usagepattern. A usage pattern comprises at least one of i) the number oftelephone calls made by the customer during a billing cycle, ii) thenumber of telephone calls received by the customer during the billingcycle, iii) telephone numbers called by the customer during the billingcycle, iv) telephone numbers calling the customer during the billingcycle, v) date of each telephone call made by the customer during thebilling cycle, vi) time of each telephone call made by the customerduring the billing cycle, vii) duration of each telephone call made bythe customer during the billing cycle, viii) identity of a calling partyterminating a call before the customer answers the call, and ix) thenumber of unused minutes remaining in the billing cycle. A processoraccesses a database of usage patterns and acquires the usage pattern. Ifa reader desires a more detailed explanation of the Personal CallManager system, the reader is directed to U.S. patent application Ser.No. 09/938,922, entitled “Methods and Systems for Providing UsagePattern Service for Telecommunications Customers”, filed Aug. 24, 2001by Michael A. Griffiths, and incorporated herein by reference in itsentirety.

The CAS processor 290 determines whether journaling is turned on at step480, and, if so, stores the collected journaling information at step485. The incoming call is disconnected at step 490.

In an alternate embodiment, the incoming call disconnect step 490includes adding call duration to the stored journaling information. Callduration is not known until disconnect.

At step 350 of FIG. 2, the CAS processor 290 performs interactiverouting. Interactive routing requires input from the incoming caller inorder to connect the incoming call. Step 350 of FIG. 2 continues at step500 of FIG. 4, which depicts a flow chart of the interactive routingfeature of an embodiment of the present invention in a wireless networkenvironment. The CAS processor 290 starts executing interactive routingmethods at step 500. And, for this particular embodiment, in step 505the CAS processor 290 determines whether the subscriber has a Voice MailSubsystem (VMS) 165.

If the subscriber does not have VMS 165, then the CAS processor 290presents an announcement in step 510 informing the caller that the calladministration service is active, and that the caller should call backafter the service activation time ends. At this point, the caller has atime-limited option to enter a bypass code in step 515, which will bereceived or captured by the CAS processor 290. Should the caller notenter an option, the CAS processor 290 times out, setting the callerinput to NULL.

If the subscriber does have VMS 165, then the CAS processor 290 displaysan announcement in step 520 informing the caller that the calladministration service is 25 active, and that the caller may leave amessage for the subscriber. The “display” of an announcement comprisesat least one of an audio display (i.e., the playing of an audio versionof the announcement) and a video or visual display (i.e., displaying anannouncement on a display screen of a thin client device, for example).The term “presents” is used in this context to mean “displays.”Additionally, an announcement 30 comprises at least one of anannouncement and a menu. Also, examples of thin client I devicesinclude, but are not limited to, cellular phones, PALM devices, handheld computers and BLUETOOTH communication devices.

In step 525, the caller has a time-limited option of entering a menuresponse number to invoke the VMS service 165 or entering a bypass code.Caller input is received or captured by the CAS processor 290 in step525, or the CAS processor 290 sets the caller input to NULL in the eventof a timeout. Note that other embodiments provide additional subscribersubsystems (beyond just a VMS service 165) which an unauthorized caller(i.e., a caller who is not in the access table for auto-routing) maychose by entering the correct subsystem number (presented in theannouncement), or the caller may be given the option of entering only a“#” symbol, for example, to escape (and disconnect). In such anembodiment, the CAS processor 290 routes the incoming call to thesubsystem associated with the caller-entered unauthorized caller routeoption. For instance, menu options may be presented to the caller forconnecting to a VMS 165 (“1#”), a fax subsystem 180 (“2#”) or a mobilephone 230 (“3#”). The incoming call is then routed according to thecaller's menu selection. Note that unauthorized caller route options areprovisioned by the subscriber.

In step 530, the CAS processor 290 determines whether “1#” has beenentered by the caller. If “1#” has been entered, the CAS processor 290enables routing of the incoming call to the VMS service 165 in step 535.

If “1#” has not been entered by the caller, the CAS processor 290determines whether a bypass code has been entered in step 540 and checksthe validity of the bypass code in step 545. The validity check isperformed by the CAS processor 290 by comparing the caller-enteredbypass code to the at least one bypass code stored in CAS storagedatabase 280 as subscriber provisioning information. Various embodimentsof the call administration service include entry mechanisms for thebypass code of at least one of DTMF, voice and speech input, where voiceinput is speaker specific, but speech input is not speaker specific.Both voice and speech recognition processing may be implemented inembodiments using commercial off the shelf voice and speech recognitionsoftware. If the correct bypass code has been entered by the caller,then in step 550 the CAS processor 290 presents an announcement that thecall is connecting, and connects the incoming call to the subscriber instep 555.

If a bypass code is not entered in a timely manner, as determined by theCAS processor 290 in step 540, then the CAS processor 290 times out instep 543. The CAS processor 290 then sets the caller input to NULL.

If an invalid bypass code is detected by CAS processor 290 in step 545,then, if the caller has only tried once to enter the correct bypass code(as determined by CAS processor 290 in step 560), the caller is given asecond chance to enter the correct bypass code. The CAS processor 290first presents (i.e., displays) an announcement in step 565, thenreceives the caller's input (or times out) in step 573. Processing thenreturns to step 540, where the CAS processor 290 determines whether abypass code entry exists.

If the bypass code is invalid for a second time, as determined by theCAS processor 290 in step 560, then the CAS processor executes step 570.In step 570, the CAS processor 290 presents an announcement suggestingthat the caller please call back at a later time.

After the CAS processor 290 has executed one of steps 535, 543, 555, or570, then the CAS processor 290 determines whether the subscriber hasrequested journaling in step 575. If the subscriber has requestedjournaling, as determined by the CAS processor 290 in step 575 (bydetermining whether a journaling semaphore has been set), then therequested journaling information is stored in CAS storage database 280at step 580.

In one embodiment, stored journaling information may be formatted andviewed via a graphical user interface (GUI). Formatting includes HTMLformatting. A subscriber may then subsequently view the HTML-formattedjournaling information using a browser on a thin or thick client. Inanother embodiment, stored journaling information may be transferredelectronically to another database for follow-on processing by a systemsuch as the Personal Call Manager.

The incoming call is disconnected at step 585 after the CAS processor290 executes step 580, or the CAS processor 290 has executed step 575and determined that journaling is not requested. In another embodiment,the incoming call disconnect step 585 includes adding call duration tothe stored journaling information.

Various embodiments of the present invention provide differentmechanisms for entering subscriber provisioning information. FIG. 5comprises an exemplary illustration of using a thin client browser forprovisioning of the present invention. Examples of thin clients include,but are not limited to, cell phones, PALM devices, hand held computers,30 and BLUETOOTH communication devices. Referring to FIG. 5, a cellulartelephone 600 is shown as a thin client device with a top levelprovisioning and activation screen 610. Several lower level menus arealso shown.

The first lower level screen 615 appears upon a subscriber's selectionof “Deactivate” in the top level screen 610. The Deactivate screen 615allows a subscriber to chose to deactivate the call administrationservice immediately or to set an end time at which the serviceautomatically deactivates.

Upon the subscriber selecting “Activate” in top level screen 610,activation screen 620 appears allowing the subscriber to set variousprovisioning options. These options comprise service activation times,command entries, script entries, configuration file name entries, andpipeline entries. In one embodiment, command entries comprise featurecode strings that instruct the call administration service to activateduring a certain provisioned time period. Scripts concatenate severalcommands, which are then executed one after the other. File names areconfiguration files. Persistent configuration files enable the calladministration service's flexibility. A configuration file is kicked offonce, and then the file sets up different call administration servicescenarios that automatically configure themselves based upon thesubscriber-specified provisioning information contained within aconfiguration file. Pipelines are analogous to scripts. However,pipelines are a concatenation of more than one configuration file name.These concatenated configuration file names execute one after the otherand may be entered as a string of file names at a computer input prompt.Note that a configuration file can also implement a pipeline by listingmultiple configuration file names as the provisioning information withinthe pipeline.

The subscriber selects the “Build File” option in the top level screen610 on the subscriber's cell phone 600 to arrive at a screen 625 forinputting provisioning information within a configuration file. Thisprovisioning information comprises set times entries, configurationentries, command entries, script entries, configuration file nameentries, pipeline entries and a save as option as shown in screen 625.

The subscriber selects the “View Files” option in top level screen 610to list files available for provisioning the call administration servicein lower level screen 630. Note that default files can be provided tothe subscriber by the service provider for common configurationscenarios. Note also that since these files are permanently stored (inCAS storage database 280, for example), configuration files can beswapped among subscribers. And, these configuration files can even becreated offline and later transferred (via email, FTP, etc.) to the CASstorage database 280, thereby decreasing the processing load on the CASprocessor 290 that can be attributed to subscriber provisioning. Anotherembodiment of the present invention arranges these configuration filesin subscriber-specified directories to organize large numbers of files.

The subscriber selects “Set Options” in top level screen 610 to exposescreen 635, which lists provisioning options that the subscriber canset. These options comprise bypass codes, access lists (includingauthorized names and numbers), routing options, journaling options andpriority options. Priority options specify which active configurationtakes precedence in a situation in which two or more configurations haveaccidentally been activated at the same time. In one embodiment, apriority option instructs the CAS processor 290 that the last activatedconfiguration prevails if there is a conflict involving provisioningparameters.

Upon selecting “Journaling Options” in screen 635, the CAS processor 290presents the subscriber with screen 640. Various journalingconfiguration options are shown in screen 640 comprising turning offjournaling, the information to log, setting the selected options as thecurrent configuration and for saving a journaling set up as a journalingconfiguration file.

The subscriber selects “View Options” in top level screen 610 and ispresented with screen 645 containing a list of categories of viewableprovisioning information. Further selection of “Access Lists” allows asubscriber to view access lists or access tables that may be used toconfigure the call administration service. Screen 650 contains fourexemplary access lists (numbered 0 through 3). Access list 0 (savedunder the filename “None”) essentially turns off automatic routing bynot permitting any authorized callers. Access list 1 automaticallyroutes incoming calls from only one number to the subscriber (i.e., theprimary auto-route number is “0”), and also contains a secondary route(to subsystem 1). Access list 2 automatically routes incoming calls fromtwo numbers, and contains a secondary route only for the first number onthe access list. Access list number 3 (saved under the filename of“Conference”) sets up a conference call by routing an incoming call fromthe specified number to three places (i.e., to subsystems 3 and 4, andto the subscriber's phone, designated as “0”).

The subscriber may select a “Maintenance” option in top level screen 610to view selectable maintenance options in screen 655. Exemplary optionscomprise deleting, organizing (i.e., inputting directory entries underwhich to organize provisioning files, such as configuration file nameentries, access list filenames, etc.) and archiving old files.

In one embodiment, forms are filled out by the subscriber to specifyprovisioning information for the call administration service. FIG. 6comprises an exemplary illustration of the use of a thin client browserin filling out a form for provisioning the present invention. As analternative to screen 640 presented in FIG. 5, a browser form for a thinclient such as a cell phone is presented in FIG. 6. Using this form 670,a subscriber merely selects check boxes for logging a caller name 680and a caller number 684, a date/time stamp 686 and a disposition 688 ofthe incoming call. The subscriber also selects the “Save as” check box692 and enters a file name, “ALL”, in text field 694 for saving theselected journaling options. The “Set as Current” check box 690 is alsochosen, because a subscriber wishes to implement these journalingoptions immediately, as well as save them in a file named “ALL” forfuture use. Selecting the check box labeled “No Journaling” 680 turnsoff journaling. When the subscriber is finished selecting journalingoptions, the subscriber selects the “Submit” button 696.

Subscriber provisioning information is stored in formatted recordswithin a file (i.e., a formatted file). FIG. 7 comprises an exemplaryconfiguration file and pipeline for flexible provisioning of the presentinvention. Referring to FIG. 7, examples of two configuration fileformats and a pipeline file format are shown. A configuration file named“FridayFile” is shown at 700. FridayFile 700 comprises a “Type” field702, which describes the type of file (1=file, 2=pipeline), a File Namefield 704 (“FridayFile”), a Periodic/Aperiodic (or P/A) code 706, whichis read by the CAS processor 290 as the time periods to execute thisparticular configuration file. For instance, the P/A code 706 shown forFridayFile 700 (“PD6W*”) tells the CAS processor 290 that the FridayFile700 should be executed periodically (“P”) on Fridays (day 6 or “D6”)every week (“W*”). This is in contrast to the aperiodic run times setfor the “GameNites” configuration file 701. The P/A code 706 forGameNites 701 is “A,DOW=2,5,7”, which indicates to the CAS processor 290that this configuration file should be executed aperiodically (“A”) onDays of the Week (“DOW”) Monday (“2”), Thursday (“5”) and Saturday(“7”).

Continuing to look at the format of the configuration file namedFridayFile 700 in FIG. 7, a date/time group field 708 is shown next. Thedate/time group field 708 comprises subfields DD (Date Duration), SD(Start Date), ED (End Date), TD (Time Duration), ST (Start Time) and ET(End Time). The DD field permits the subscriber to provision a dateduration (i.e., tells the CAS processor 290 to execute the file for DDdays starting now). The SD and ST subfields are also known as invocationpoints, which tell the CAS processor 290 the date and time,respectively, to start executing the file. The ED and ET subfields arealso known as termination points, which tell the CAS processor 290 thedate and time, respectively, to stop executing the file.

The other fields within a configuration file in this particularembodiment of the present invention include: a bypass field 710,comprising a bypass options file name in this example; an unauthorizedcaller routing options field 712, comprising a file name for routingoptions available to the unauthorized (or interactively routed) caller;an access list field 714, comprising access list files of theidentification of authorized callers that will have their callsautomatically routed; and a journaling field 716, comprising a name of afile of journaling options. An alternate embodiment further comprises anauto-routing options field comprising a file of subsystemidentifications. Such subsystems comprise the terminating points of anauto-routed incoming call. Further embodiments comprise an auto-routingoptions field comprising at least one of an alias (to a device such as apager or to a voice mail subsystem, as examples) or an address (such asa phone number or device's network address).

An embodiment of a configuration that implements a pipeline is alsoshown in FIG. 7. “JulyPipeLine” 703 contains a Type field of “2”,indicating that this “file” is of type “pipeline”. Although a pipelinemay be implemented dynamically, by listing multiple files on a commandline to be executed consecutively, a configuration file can also containthe names of multiple files to be consecutively executed by the CASprocessor 290. Once the CAS processor 290 recognizes the file as havinga type of “2” as shown in Type field 720, the processor 290 determinesthe name of the pipeline from the PipeLine Name field 725 (in this case“JulyPipeLine”). Since a pipeline (or record of type “2”) has norequired maximum length, the CAS processor 290 must read each file namein the File Names field 730 until a record delimiter (such as “##”) isencountered. In the present example, the JulyPipeLine record 703contains references to four configuration files entitled “Week1”,“Week2”, “Week3”, and “Week4” in the File Names field 730. Therefore,when the CAS processor 290 is presented with the JulyPipeLine 703record, the CAS processor 290 will actually execute the files Week1,Week2, Week3, and Week4 consecutively. The configuration times androuting, access, bypass, journaling, etc., options are set internally tothe Week1, Week2, Week3, and Week4 configuration files.

FIG. 8 comprises a flow chart of theactivation/deactivation/provisioning process for an embodiment of thepresent invention. In step 800 the CAS processor 290 receives anactivator from the subscriber provisioning information, such as a *88feature code command as DTMF input in one embodiment. In an alternativeembodiment, the subscriber dials a CAS activation number and requestsactivation via spoken words such as “Activate CAS”. These spoken wordsin the alternative embodiment are collected by the CAS processor 290 andprocessed by a voice processing software subsystem residing on the CASprocessor 290. Next, the CAS processor 290 in step 803 presents anannouncement stating “You have requested activation of the calladministration service”. Presenting an announcement comprises displayingan announcement.

The CAS processor 290 performs security and validation routines, such assubscriber identification and password checking, in step 806. Once thesubscriber has been validated, in step 809 the subscriber is presentedwith menu options comprising activation, file quick start, deactivation,provisioning and quitting the menu.

In step 812, the CAS processor 290 determines whether the subscriber haschosen selection #1 “Activation”. If so, the CAS processor 290 presentsanother menu to the subscriber in step 815, asking the subscriber tochose an activation mode (i.e., by command, script, configuration fileor pipeline). In step 818 the CAS processor 290 determines whether acommand will be used to activate the caller administration service. Ifso, then the command entry routines are executed in step 821. If not,then the CAS processor 290 determines whether a script will be used toactivate the caller administration service in step 824. If scriptactivation is selected by the subscriber, then the script entry routinesare executed in step 827. If not, then the CAS processor 290 determinesin step 830 whether file activation will be used. If configuration fileactivation is selected, then the file entry routines are executed by theCAS processor 290 in step 833. If not, then the CAS processor 290determines whether pipeline activation will be used in step 836. Ifpipeline activation is selected, then the pipeline entry routines areexecuted by the CAS processor 290 in step 839. After the CAS processor290 has determined one of steps 818, 824, 830 or 836 to be the selectedactivation method (and the appropriate entry routines of steps 821, 827,833 or 839 have been executed), then the CAS processor 290 activates thecall administration service in step 854.

In step 842, the CAS processor 290 determines whether the subscriber haschosen selection #2 “File Quick Start” from the menu presented in step809. If so, then the CAS processor 290 presents an announcement in step845, requesting input of a file number or “L” to list available files.If the CAS processor 290 determines that an “L” has been input in step848, then the available files are listed, as per step 851, and controlloops back to step 845 for the presenting of an announcement prompting asubscriber for input of a file number (or “L”). If “L” has not beeninput by the subscriber, then the CAS processor 290 validates the filenumber input in step 852. Once a valid file number is received in step852, then the CAS processor 290 activates the call administrationservice in step 854. If the file number is invalid, as determined by theCAS processor in step 852, then control returns to step 845.

In step 857, the CAS processor 290 determines whether the subscriber haschosen selection #3 “Deactivation” from the menu presented in step 809.If so, then the CAS processor 290 deactivates the service in step 860.

In step 863, the CAS processor 290 determines whether the subscriber haschosen selection #4 “Provisioning” from the menu presented in step 809.If so, then the CAS processor 290 executes the provisioning routines instep 866. An embodiment of provisioning using a browser on a thin clientsuch as a cellular telephone is discussed in detail in FIG. 5 and FIG.6.

After the call administration service has been activated in step 854,deactivated in step 860, or provisioned in step 866, the subscriber isgiven the option of exiting in step 871. If subscriber answers in theaffirmative, the CAS processor 290 exits in step 878. If the subscriberanswers in the negative, then the CAS processor 290 returns thesubscriber to the menu presented at step 809.

The subscriber also has the option of quitting from the menu of step809. If the CAS processor 290 determines that in step 873 the subscriberhas chosen #5 “Quit” from the menu of step 809, the CAS processor 290exits at step 878. If subscriber enters an invalid selection whenpresented with the menu of step 809 as determined in step 873, then theCAS processor 290 causes an “Invalid option” message to be presented andreturns the subscriber to the menu at step 809.

FIG. 9 illustrates an embodiment of the present invention in the PublicSwitched Telephone Network (PSTN) 10 environment of a Regional BellOperating Company (RBOC), such as BellSouth. The delivery of landlinecommunications is accomplished via two major subsystems: the PSTN 10 andthe Signaling System 7 (SS7) Network 20. The PSTN 10 transfers payloadcommunications (voice and data) via switching nodes called ServiceSwitching Points (SSP) 30. An SSP 30 may be a Lucent Technologies 5ESS®switch or other comparable switch. The SS7 network 20 is a packetswitching network, which uses Signaling Transfer Point (STP) 40 elementsto transfer SS7 messages used for management and control of the PSTN 10.SS7 network 20 may also interface to an Other SS7 Network 50, whichpredominantly carries packet switched data for controlling Other Network60.

Another element of the PSTN 10 is the Access Tandem (AT) switch 70. AnAT switch 70 may be a Lucent Technologies 5ESS g2000 switch or othercomparable switch. The AT switch 70 is used to interface to othernetworks 60 and to consolidate 15 external communications traffic fortransport via the PSTN 10. Other networks 60 include those of the sametelephone technology, such as other RBOCs and long distance telephonecompanies. Other networks 60 also include networks of the differenttechnologies, such as wireless (comprising the various cellulartechnologies, 3G, BLUETOOTH communication technology and PCS), ISDN(Integrated Services Digital Network), data networks, X.25, 20 FrameRelay, and ATM (Asynchronous Transfer Mode).

The local switching management center 110 is comprised of elements suchas the Service Management System (SMS) 80, the Service Control Point(SCP) 90 and Other Subsystems 100. The SMS 80 manages software updates,service data updates, subscriber data updates and subscriber servicereports. The SCP 90 is a server and an associated database, SCP storage98. The SCP 90 interfaces with the SSP network element 30 via the SS7network 20, and translates SSP 30 Transaction Capabilities ApplicationsProtocol (TCAP) queries into routing instructions for the SSP 30. Thelocal switching management center 110 also contains Other Subsystems 100such as reporting and billing subsystems.

Additionally, the PSTN 10 interfaces to various types of user equipmentand user subsystems via end office switches 120. User equipment includestelephones 130, 130A, and 130B, answering machines 140, and fax machines150. User subsystems include recording 160, voice mail 165, video 170,fax 180 and Private Branch eXchanges (PBXs) 190 subsystems.

In one embodiment of the present invention, an SCP 90 hosts a ServicePackage Application (CAS SPA) 95 software subsystem. The CAS SPA 95 is aimplements an embodiment of a method of the present invention. SCPstorage 97 comprises persistent subscriber provisioning information. Analternative embodiment provides a CAS secondary storage 98 for storingcaller administration service subscriber provisioning information.

In another embodiment of the present invention, a call administrationservice (CAS) processor 112 and a CAS storage database 114 are connectedvia a network connection (e.g., Ethernet, Fiber Distributed DataInterface, Asynchronous Transfer Mode, etc.) to the SMS 80 and SCP 90network elements. The CAS processor 112 implements the methods of anembodiment of the present invention, while the CAS storage database 114stores CAS subscriber provisioning information.

In a call flow scenario of the PSTN 10, an embodiment of a CAS SPA 95implementation of the present invention proceeds as follows: A caller,using telephone 130A, dials a subscriber on telephone 130B. When the SSP30 associated with subscriber telephone 130B detects a triggerassociated with the incoming call, the SSP 30 associated with subscribertelephone 130B launches an AIN (Advanced Intelligent Network) query. AnAIN query begins with a Transaction Capability Application Part (TCAP)query message that is sent via a Transactional Manager (TM) subsystem 35within the SSP 30 to the SCP 90 by way of an STP 40 and the SS7 controlnetwork 20.

The STP 40 receives the TCAP query message, and then translates thesubscriber's address to determine the correct SCP 90 address and theappropriate Service Package Application for processing the AIN servicerequest. In this case, the CAS SPA 95 is the appropriate ServiceApplication Package. The STP 40 reformulates and forwards the TCAPmessage to the appropriate SCP 90 over the SS7 network. The SCP 90creates a routing key from the TCAP message and passes the routing keyinformation along to the CAS SPA 95. The CAS SPA 95 uses the routing keyto identify the subscriber of the call administration service (i.e., thecalled party).

Interaction between the CAS SPA 95 and the SSP 30 (with the STP 40 andSCP 90 as intermediaries) takes place throughout the implementation ofthe call administration service. For instance, during interactiverouting, which is explained in the discussion of FIG. 12, an“unauthorized” caller (i.e., a caller who's identification informationis not found in the current access list) has the option of entering abypass code in order to be connected to the subscriber or entering anunauthorized caller routing option in order to be connected to asubscriber subsystem, such as a Recording Subsystem. The underlyingimplementation in this embodiment of the present invention comprises theCAS SPA 95 requesting that the SCP 90 send a TCAP conversation messageby way of the STP 40 to the SSP 30. The purpose of this particular TCAPconversation message is to instruct the SSP 30 to present anannouncement and to collect an unauthorized caller input. Upon receiptof the TCAP conversation message from the SCP 90, the SSP 30 presents anannouncement and collects an unauthorized caller input. The SSP 30 thenreturns a conversation message containing the caller input, and the CASSPA 95 proceeds with interactive routing processing based upon thecontents of the conversation message returned by SSP 30.

Such interaction takes place between a CAS SPA 95 and an SSP 30 when theCAS SPA 95 implements the call administration service. In order to notunnecessarily obscure the present invention, the well known processoperations comprising the exchange of TCAP messages between a CAS SPA 95and an SSP 30 in FIG. 10 through FIG. 12 are discussed from theperspective of the CAS SPA 95 only.

In the embodiment shown, before a subscriber's incoming calls areadministered, the subscriber must initiate provisioning. Provisioningcomprises using a data entry subsystem to set system configurationparameters in order to instruct the present invention as to how toprocess incoming calls. Typically, the subscriber provisions the systemin real-time. However, alternate embodiments permit the subscriber toforward provisioning information to the CAS SPA 95 for storage andsubsequent usage at a later time.

One embodiment of the present invention comprises a DTMF (Dual ToneMultiple Frequency) menu response system for data entry. Otherembodiments provide for voice processing and speech processing dataentry using, preferably, commercial off the shelf software as a softwaresubsystem of the CAS SPA 95. Additionally, a browser form data entrymechanism for provisioning, and a formatted file translation data entrymechanism for provisioning are available as embodiments of the presentinvention. The browser form data entry mechanism may be implemented on athin client device or a cellular phone in alternate embodiments. Aformatted file is a file in which each field of the file is associatedwith a certain type of data. For instance, field 1 may comprise asubscriber's identification (comprising at least one of a name and anumber), field 2 may comprise a file type identifier, field 3 maycomprise a set of bypass codes, etc. A formatted file translation dataentry mechanism comprises at least one of electronic delivery of a filewith a standard internal format and hard copy delivery of a formattedfile. Electronic delivery of a file further comprises at least one ofemail, a file transfer mechanism (such as File Transfer Protocol (FTP)),a diskette and a CD. Hard copy delivery further comprises a paper copythat is scanned for provisioning data in predefined fields.

After receiving provisioning information from the subscriber, CAS SPA 95stores the provisioning information in SCP storage 97, which comprisessecondary storage associated with the SCP 90. Alternatively, a separatesecondary storage device, CAS secondary storage 98, used exclusively forthe call administration service is provided in another embodiment of thepresent invention.

Once provisioned, the present invention must be activated to processincoming calls in accordance with the provisioning information. Asubscriber invokes or activates the call administration serviceinteractively, using one of the data entry mechanisms previouslydiscussed in regards to subscriber provisioning.

To activate one embodiment the present invention, the subscriber sendsto the CAS SPA 95 a system activator and activation times comprising atleast one of an invocation point (or start time and/or date) and atermination point (or ending time and/or date). The present invention isactivated by the CAS SPA 95 either immediately (if no invocation pointor an immediate start time is sent by the operator to the CAS SPA 95) orat a later time specified by the invocation point. A flag is set toindicate activation status. System activators comprise at least one of acommand, a script, a configuration file name and a pipeline. In oneembodiment, optional times may be provided as direct input to the CASSPA 95 in response to a menu driven series of questions (i.e., “Startthe call administration at what time? [Hit # to start now].”). Inanother embodiment, optional times may be embedded within aconfiguration file, which the user submits to the CAS SPA 95.

After the present invention has been both provisioned and activated, thecall administration service may then be implemented by the CAS SPA 95.FIG. 10 comprises an overall flow diagram of an embodiment of a methodof the present invention, which is implemented by the CAS SPA 95starting with step 1 000.

In step 1010, the CAS SPA 95 receives the subscriber provisioninginformation from SCP storage 97. In alternative embodiments, the CAS SPA95 receives the subscriber provisioning information from CAS secondarystorage 98, or the subscriber provisioning information is set directlyby the subscriber in main memory as the current configuration. Next, instep 1015, the CAS SPA 95 receives incoming call information. Incomingcall information comprises a caller identification, such as a callernumber or caller name, extracted from the TCAP information.

At step 1020, the CAS SPA 95 determines if the subscriber has activatedthe call administration service. In one embodiment, the CAS SPA 95implements this step by checking a flag, which indicates the calladministration service activation status. If the system has not beenactivated, then in step 1030 the CAS SPA 95 communicates this inactivestatus to the SCP 90, which, in turn, instructs the SSP 30 via a TCAPmessage to connect the incoming call to the subscriber.

If the call administration service is active, the CAS SPA 95 will routethe call in accordance with the subscriber provisioning information,which includes an access table. The CAS SPA 95 begins in step 1040 bysearching a currently active access table for the caller identification,such as a caller number. In another embodiment, a caller identificationcomprises a caller name. If the caller identification is not foundwithin the access table, then the CAS SPA 95 performs interactiverouting in step 1050. Otherwise, the caller identification is found inthe access table, and the CAS SPA 95 performs automatic routing in step1060.

Step 1060 of FIG. 10 continues at step 1100 of FIG. 11. An embodiment ofan automatic routing mechanism is shown in the flow chart of FIG. 11.The CAS SPA 95 starts executing the automatic routing routines at step1100. In step 1110, the CAS SPA 95 receives auto-routing options fromthe subscriber provisioning information from the SCP storage 97.

At step 1120, the CAS SPA 95 determines if there is exactly one primaryauto route number in the subscriber provisioning information (i.e., inthe currently active access file associated with an authorized calleridentification, where an authorized caller is a caller whose calleridentification has been entered (i.e., provisioned) into an accesstable). If exactly one primary auto-route number associated with theauthorized caller exists, then in step 1130 the CAS SPA 95 requests thatthe SCP 90 send a TCAP message 5 to the SSP 30 to connect the incomingcall to the primary auto-route number subsystem. In one embodiment, anauto-route number of “O” indicates that the subsystem to which theincoming caller should be connected is the subscriber's home phone. Notethat; subsystems comprise service provider systems (such as voice mailsubsystems) and end user “systems” (such as home phones, cellularphones, BLUETOOTH communication devices, and PBXs).

If the CAS SPA 95 at step 1120 determines that there is not exactly oneprimary auto-route number associated with the authorized caller, then atstep 1140 the CAS SPA 95 determines if there is more than one primaryauto-route number associated with the caller identification within theaccess table.

If there is more than one primary auto-route number, then in step 1150the CAS SPA 95 requests that the SCP 90 forward multiple TCAP messages(one per primary auto-route number, in one embodiment) to the SSP 30 toconnect the incoming call to the auto-route numbers of subsystems in amulticast fashion. Such a mechanism would serve to establish an audio orvideo conference, for example.

If the CAS SPA 95 has determined that the subscriber has provisioned noprimary auto-routes for the caller in the access list (i.e., the answersto the determinations made by the CAS SPA 95 in steps 1120 and 1140 areboth “no”), then step 1165 is executed. In step 1165, the CAS SPA 95determines whether a secondary auto-route number, associated with theauthorized caller, exists in the access table. If a secondary auto-routenumber exists in the access table, then the CAS SPA 95 requests that theSCP 90 forward a TCAP message to the SSP 30 to connect the incoming callto the subsystem denoted by the secondary auto-route number. In thismanner, a fail safe routing capability is implemented to connect anincoming call to a backup subsystem (i.e., the secondary subsystem).

Note that in one embodiment, the CAS SPA 95 determines whethersubsystems are available. Routing of an incoming call takes place onlyif a subsystem is (or subsystems are) available. A subsystem isavailable if an incoming call can be connected to or terminated at thesubsystem. Exemplary reasons a subsystem may be unavailable orunreachable include i) called party does not subscribe to a serviceimplemented by that subsystem (i.e., VMS), ii) communications path isdown, and iii) device (i.e., phone) is “off hook”. CAS SPA 95 determinesthat a called party does not subscribe to a service by querying asubscriber service database. CAS SPA 95 determines that a communicationspath is down or that a device is off hook upon receipt of an appropriateTCAP message.

Next, the CAS SPA 95 executes step 1180 to determine if the subscriberhas requested journaling. This step takes place after either theincoming call has been connected to a subsystem (in steps 1130, 1150 or1175), if the requested secondary subsystem is determined by the CAS SPA95 to be unavailable in step 1170, or if the CAS SPA 95 has determinedthat the secondary auto-route number is not set in step 1165.

If the subscriber has requested journaling, the CAS SPA 95 stores therequested journal information in SCP storage 97. Journaling is thelogging of information about the incoming call. The logged informationcomprises at least one of a caller name, a caller number, a date/timestamp and the incoming call disposition (i.e., whether and where theincoming call was connected). An alternate embodiment comprises storingjournal information in CAS secondary storage 98, which provides storageexclusively for the call administration service.

In another embodiment, stored journaling information may be formattedand viewed via a graphical user interface (GUI). Formatting includesHTML formatting. A subscriber may then subsequently view theHTML-formatted journaling information using a browser on a thin or thickclient. In another embodiment, stored journaling information may betransferred electronically to another database for follow-on processingby a system such as the Personal Call Manager.

If the subscriber has not requested journaling, as determined by the CASSPA 95 in step 1180, the incoming call is disconnected in step 1190. Ifthe subscriber has requested journaling, then the CAS SPA 95 stores thejournal information in step 1185, and the incoming call is thendisconnected in step 1190. In an alternate embodiment, the incoming calldisconnect step 1190 includes adding call duration to the storedjournaling information.

Step 1050 of FIG. 10 continues at step 1200 of FIG. 12. An embodiment ofan interactive routing mechanism is shown in the flow chart of FIG. 12.The CAS SPA 95 starts the interactive routing methods at step 1200. Forthis particular embodiment, in step 1205, the CAS SPA 95 determineswhether the subscriber has a Recording Subsystem Service (RSS).

If the subscriber dose not subscribe to RSS, then the CAS SPA 95 in step1210 initiates a message, requesting that the SCP 90 send a TCAPconversation message to 5 SSP 30 requesting that an ammouncement bepresented by the SSP 30 and that SSP 30 collect a bypass code from thecaller, if the coller enter such a bypass code. In one embodiment, theammouncement presented in step 1210 tells the caller that the calladministration service is active and that the caller should call backafter the service activation time ends. In another embodiment,announcement may be “displayed”. Note 10 that an audio announcement is“displayed” by playing the announcement. A video or visual announcement(or text display announcement) is displayed by displaying theannouncement on a display screen (of a thin client device, for example).Additionally, an announcement comprises at least one of an announcementand a menu. Also, example of thin client device include, but are notlimited to, cellular phones, hand held computers, 15 PALM device, andBLUETOOTH communication device.

At this point, the caller has a time-limited option to enter a bypasscode in step 1215. The entered bypass code will be received or capturedby the CAS SPA 95 by way of the SCP 90 via the return TCAP conversationmessage from the SSP 30. Should the caller not enter an option in atimely manner, the CAS SPA 95 times out and sets the caller input toNULL.

If the subscriber does subscribe to RSS, then the CAS SPA 95 in step1220 initiates a message, requesting that the SCP 90 send a TCAPconversation message to SSP 30 requesting that an announcement bepresented by the SSP 30 and that SSP 30 collect input from the caller,if the caller enters such input. Valid input comprises at least one of amenu option that indicates a caller-selected subsystem to which theincoming call is being requested to be routed, and a bypass code. TheCAS SPA 95 receives or captures the caller input in step 1225 by way ofthe SCP 90 via the return TCAP conversation message from the SSP 30.Again, should the caller not enter input in a timely manner, the CAS SPA95 times out and sets the caller input to NULL.

In one embodiment, the caller has an option of entering “1#” to invokethe RSS service. Note that other embodiments provide additionalsubscriber subsystems (beyond just a RSS service) which an unauthorizedcaller (i.e., a caller who is not in the access table for auto-routing)may chose by entering the correct number (presented in theannouncement), or the caller may be given the option of entering only a“#” symbol to escape (and disconnect). In such an embodiment, the CASSPA 95 routes the incoming call to the subsystem associated with thecaller-entered unauthorized caller route option. For instance, menuoptions may be presented to the caller for connecting to a RSS (“1#”), afax subsystem (“2#”) or a mobile phone (“3#”), and the incoming call isthen routed according to the caller's menu selection.

Note that unauthorized caller route options are provisioned by thesubscriber.

In step 1230, the CAS SPA 95 determines whether “1#” has been entered bythe caller. If so, the CAS SPA 95 enables routing of the incoming callto the RSS in step 1235. The actual routing takes place using the TCAPmechanism and the SCP 90 and SSP 30 network elements, as previouslydescribed for automatic routing in the discussion of FIG. 11.

If “1#” has not been entered by the caller, the CAS SPA 95 determineswhether a bypass code has been entered in step 1240, and checks thevalidity of the bypass code in step 1245. The validity check isperformed by the CAS SPA 95 by comparing the caller-entered bypass codeto an at least one bypass code stored in SCP storage 97 as subscriberprovisioning information. Various embodiments of the call administrationservice include a data entry mechanism for the menu selection and thebypass code of at least one of DTMF, voice and speech input, where voiceinput is speaker specific, but speech input is not speaker specific.Both voice and speech recognition processing may be implemented bycommercial off the shelf voice and speech recognition softwareintegrated as a software subsystem of the CAS SPA 95. If the correctbypass code has been entered by the caller, then in step 1250 the CASSPA 95 presents an announcement that the call is connecting, and theincoming call is connected to the subscriber in step 1255.

If no bypass code is entered in step 1240, then the CAS SPA 95 times outin step 1243. The incoming call will ultimately not be connected at thispoint.

If an invalid bypass code is detected by the CAS SPA 95 in step 1245,then the CAS SPA 95 determines if this is the caller's first attempt atentering a bypass code. If the caller has already entered one incorrectbypass code, as determined by the CAS SPA 95 in step 1260, then the CASSPA 95 presents an announcement at step 1270, instructing the caller tocall back at a later time. In one embodiment, the later call back timecan be specified as the time when the caller administration service isscheduled to deactivate.

If the caller has only tried once to enter the correct bypass code (asdetermined by the CAS SPA 95 in step 1260), the caller is given a secondchance to enter the correct bypass code. First, the CAS SPA 95 requeststhat an announcement be presented in step 1265, which instructs thecaller to reenter the bypass code. Then the CAS SPA 95 receives thecaller's input (or times out) in step 1273. Processing then returns tostep 1240, where the CAS SPA 95 determines whether a bypass code entryexists.

After the CAS SPA 95 executes one of steps 1235 or 1255 (and connectsthe incoming call to a subsystem or to the subscriber), or executes oneof steps 1243 or 1270 (and fails to connect the incoming call), then CASSPA 95 determines whether the subscriber has requested journaling instep 1275. If the subscriber has requested journaling, as determined bythe CAS SPA 95 in step 1275 (by determining whether a journalingsemaphore has been set), then the requested journal information isstored in SPC storage 97, or alternatively in CAS secondary storage 98,at step 1280.

In one embodiment, stored journaling information may be formatted andviewed via a graphical user interface (GUI). Formatting includes HTMLformatting. A subscriber may then subsequently view the HTML-formattedjournaling information using a browser on a thin or thick client. Inanother embodiment, stored journaling information may be transferredelectronically to another database for follow-on processing by a systemsuch as a Personal Call Manager.

The incoming call is disconnected at step 1285 after the CAS SPA 95executes step 1280 (and stores journal information) or after the CAS SPA95 executes step 1275 (and determines that journaling is not requested).In another embodiment, the incoming call disconnect step 1285 includesadding call duration to the stored journaling information.

Various embodiments of the present invention have been described infulfillment of the various objects of the invention. It should berecognized that these embodiments are merely illustrative of theprinciples of the present invention. Numerous modifications andadaptations thereof will be apparent to those skilled in the art withoutdeparting from the spirit and scope of the present invention.

What is claimed is:
 1. A method for implementing call managementcomprising: receiving an incoming call from a caller; receiving incomingcall information (ICI), wherein ICI comprises a caller identification(CI); extracting the CI from the ICI; receiving subscriber provisioninginformation (SPI); and routing the incoming call in accordance with theSPI, wherein routing the incoming call comprises at least one of;interactive routing, wherein interactive routing comprises: displayingan announcement to the caller; receiving optional input from the caller;and routing the incoming call in accordance with the optional callerinput of the caller; and automatic routing, wherein automatic routingcomprises: receiving an access table from the SPI; validating the calleras an authorized caller in the access table in accordance with the CI;receiving from the access table an at least one auto-route optionassociated with the authorized caller; and connecting the incoming callin accordance with the at least one auto-route option associated withthe authorized caller.
 2. The method of claim 1, wherein receivingsubscribe provisioning information comprises: establishing an interfaceto a data entry subsystem; receiving the SPI from the data entrysubsystem; and storing the SPI.
 3. A method for implementing callmanagement comprising: receiving an incoming call from a caller;receiving incoming call information (ICI), wherein the ICI comprises acaller identification (CI); extracting the CI from the ICI; receivingsubscriber provisioning information (SPI), wherein receiving subscriberprovisioning information (SPI) comprises: establishing an interface to abrowser implemented oil a client device; receiving the SPI through thebrowser of the client device; and storing the SPI; and routing theincoming call in accordance with the SPI, wherein routing the incomingcall comprises at least one of: interactive routing; and automaticrouting, wherein automatic routing comprises: receiving an access tablefrom the SPI; validating the caller as an authorized caller in theaccess table in accordance with the CI; receiving from the access tablean at least one auto-route option associated with the authorized caller;and connecting the incoming call in accordance with the at least oneauto-route option associated with the authorized caller.
 4. The methodof claim 1, wherein receiving subscriber provisioning information (SPI)comprises: establishing an interface to a browser implemented on acellular phone; receiving the SPI through the browser; and storing theSPI.
 5. The method of claim 1, wherein the optional caller inputcomprises at least one of: a bypass code; a bypass route option; and anunauthorized caller route option.
 6. The method of claim 1, wherein theoptional caller input comprises a spoken bypass code.
 7. A method forimplementing call management comprising: receiving an incoming call froma caller; receiving incoming call information (ICI), wherein the ICIcomprises a caller identification (CI); extracting the CI from the ICI;receiving subscriber provisioning information (SPI); and routing theincoming call in accordance with the SPI, wherein routing the incomingcall comprises at least one of: interactive routing; and automaticrouting, wherein automatic routing comprises: receiving an access tablefrom the SPI; validating the caller as an authorized caller in theaccess table in accordance with the CI; receiving from the access tablean at least one auto-route option associated with the authorized caller;and connecting the incoming call in accordance with the at least oneauto-route option associated with the authorized caller, wherein the atleast one auto-route option associated with the authorized callercomprises at least two auto-route options for establishing a multicastroute.
 8. The method of claim 1, wherein receiving subscriberprovisioning information (SPI) includes receiving the subscriberprovisioning information having at least one secondary auto-routeoption.
 9. A system for implementing call management, comprising: anincoming call receiver capable of receiving an incoming call from acaller; an incoming call information (ICI) receiver capable of receivingICI, wherein the ICI comprises a caller identification (CI); a CIextractor capable of extracting the CI from the ICI; a subscriberprovisioning information (SPI) receiver capable of receiving SPI; and anincoming call router, comprising at least one of: an internative router,wherein the interactive router comprises: a display for communication anannouncement to the caller; an input receiver capable of capturinginput; and a connecting router capable of connecting the incoming callin accordance with the captured input; and an automatic router, whereinthe automatic router comprises: an access table receiver capable ofreceiving an access table from the SPI; an authorized caller validatorcapable of validating the caller as authorized in the access table inaccordance with the CI; an auto-route option receiver capable ofreceiving at least one auto-route option associated with the authorizedcaller from the access table; and an incoming call terminator capable oftermination the incoming call in accordance with the at least oneauto-route option associated with authorized caller from the accesstable.
 10. A system for implementing call management, comprising: anincoming call receiver capable of receiving an incoming call from acaller; an incoming call information (ICI) receiver capable of receivingICI, wherein the ICI comprises a caller identification (CI); a CIextractor capable of extracting the CI from the ICI; a subscriberprovisioning information (SPI) receiver capable of receiving SPI,wherein the SPI receiver receives the SPI interfacing a browserimplemented on a client device; and an incoming call router, comprisingat least one of: an interactive router; and an automatic router, whereinthe automatic router comprises: an access table receiver capable ofreceiving an access table from the SPI; an authorized caller validatorcapable of validating the caller as authorized in the access table inaccordance with the CI; an auto-route option receiver capable ofreceiving at least one auto-route option associated with the authorizedcaller from the access table; and an incoming call terminator capable ofterminating the incoming call in accordance with the at least oneauto-route option associated with the authorized caller from the accesstable.
 11. The system of claim 10, wherein the client device comprises acaller phone a PALM device, a hand held computer or a Bluetooth device.12. The system of claim 9, wherein the captured input comprises at leastone of: a bypass code; a bypass route option; and an unauthorized callerroute option.
 13. The system of claim 12, wherein the bypass codecomprises a spoken bypass code.
 14. A system for implementing callmanagement, comprising: an incoming call receiver capable of receivingan incoming call from a caller; an incoming call information (ICI)receiver capable of receiving ICI, wherein the ICI comprises a calleridentification (CI); a CI extractor capable of extracting the CI fromthe ICI; a subscriber provisioning information (SPI) receiver capable ofreceiving SPI; and an incoming call router, comprising at least one of:an incoming call router; and an automatic router, wherein the automaticrouter comprises: an access table receiver capable of receiving anaccess table from the SPI; an authorized caller validator capable ofvalidating the caller as authorized in the access table in accordancewith the CI; an auto-route option receiver capable of receiving at leastone auto-route option associated with the authorized caller from theaccess table; and an incoming call terminator capable of terminating theincoming call in accordance with the at least one auto-route optionassociated with the authorized caller from the access table, wherein theat least one auto-route option associated with the authorized callercomprises at least two auto-route option, for establishing a multicastroute.
 15. The system of claim 9, wherein the at least one auto-routeoption associated with the authorized caller from the access tablefurther comprises at least one secondary auto route option.
 16. A systemfor implementing call management comprising: an incoming call receivercapable of receiving an incoming call from a caller; an incoming callinformation (ICI) receiver capable of receiving ICI, wherein the ICIcomprises a caller identification (IC); a CI extractor capable ofextracting the CI from the ICI; a subscriber provisioning information(SPI) receiver capable of receiving SPI; and an incoming call router,comprising at least one of: an interactive router; and an automaticrouter, wherein the automatic router comprises: an access table receivercapable of receiving an access table from the SPI; an authorized callervalidator capable of validating the caller as authorized in the accesstable in accordance with the CI; an auto-route option receiver capableof receiving at least one auto-route option associated with theauthorized caller from the access table; and an incoming call terminatorcapable of terminating the incoming call in accordance with the at leastone auto-route option associated with the authorized caller from theaccess table, wherein the interactive router comprises: a display forcommunicating an announcement to the caller; an input receiver capableof capturing input; and a connecting router capable of connecting theincoming call in accordance with the captured input.
 17. The system ofclaim 16, wherein the at least one auto-route option associated with;the authorized caller from the access table further comprises at leastone secondary auto route option.
 18. A method for implementing callmanagement comprising: receiving a incoming call from a caller;receiving incoming call information (ICI), wherein the ICI comprises acaller identification (CI); extracting the CI from ICI; receivingsubscriber provisioning information (SPI), wherein receiving subscriberprovisioning information comprises: establishing an interface to a dataentry subsystem; receiving the SPI from the data entry subsystem; andstoring the SPI; and routing the incoming call in accordance with theSPI, wherein routing the incoming call comprises at least one of:interactive routing; and automatic routing, wherein automatic routingcomprises: receiving an access table from the SPI; validating the calleras an authorized caller in the access table in accordance with the CI;receiving from the access table an at least one auto-route optionassociated with the authorized caller; and connecting the incoming callin accordance with at least one auto-route option associated with theauthorized caller.
 19. A method for implementing call managementcomprising: receiving a incoming call from a caller; receiving incomingcall information (ICI), wherein the ICI comprises a calleridentification (CI); extracting the CI from ICI; receiving subscriberprovisioning information (SPI), wherein receiving subscriberprovisioning information (SPI) comprises: establishing an interface to abrowser implemented on a client device; receiving the SPI from thebrowser of the client device; and storing the SPI; and routing theincoming call in accordance with the SPI, wherein routing the incomingcall comprises at least one of: interactive routing; and automaticrouting, wherein automatic routing comprises: receiving an access tablefrom the SPI; validating the caller as an authorized caller in theaccess table in accordance with the CI; receiving from the access tablean at least one auto-route option associated with the authorized caller;and connecting the incoming call in accordance with at least oneauto-route option associated with the authorized caller.
 20. A methodfor implementing call management comprising: receiving an incoming callfrom a caller; receiving incoming call information (ICI), wherein theICI comprises a caller identification (CI); extracting the CI from theICI; receiving subscriber provisioning information (SPI); and routingthe incoming call in accordance with the SPI, wherein routing theincoming call comprises at least one of: interactive routing; andautomatic routing, wherein automatic routing comprises: receiving anaccess table from the SPI; validating the caller as an authorized callerin the access table in accordance with the CI; receiving from the accesstable an at least one auto-route option associated with the authorizedcaller; and connecting the incoming call in accordance with the leastone auto-route option associated with the authorized caller, whereininteractive routing comprises: displaying an announcement to the caller;receiving the optional input from the caller; and routing the incomingcall in accordance with the optional caller input.
 21. The system ofclaim 16 wherein call management is performed in a wireless environment.22. The system of claim 16 wherein call management is performed in apublic switched telephone network.
 23. A system for implementing callmanagement, comprising: an incoming call receiver capable of receivingan incoming call from a caller; an incoming call information (ICI)receiver capable of receiving ICI, wherein the ICI comprises a calleridentification (CI); a CI extractor capable of extracting the CI fromthe ICI; a subscriber provisioning information (SPI) receiver capable ofreceiving SPI; and an incoming call router, comprising at least one of:an interactive router; and an automatic router, wherein automatic routercomprises: an access table receiver capable of receiving an access tablefrom the SPI; an authorized caller validator capable of validating thecaller as authorized in the access table in accordance with the CI; anauto-route option receiver capable of receiving at least one auto-routeoption associated with the authorized caller from the access table; andan incoming call terminator capable of terminating the incoming call inaccordance with the at least one auto-route option associated with theauthorized caller from the access table, wherein the at least oneauto-route option associated with the authorized caller comprises atleast two auto-route option for establishing a multicast route.
 24. Asystem for implementing call management, comprising: an incoming callreceiver capable of receiving an incoming call from a caller; anincoming call information (ICI) receiver capable of receiving ICI,wherein the ICI comprises a caller identification (CI); a CI extractorcapable of extracting the CI from the ICI; a subscriber provisioninginformation (SPI) receiver capable of receiving SPI; and and an incomingcall router, comprising at least one of: an incoming call router; and anautomatic router, wherein the automatic router comprises: an accesstable receiver capable of receiving an access table from the SPI; anauthorized caller validator capable of validating the caller asauthorized in the access table in accordance with the CI; an auto-routeoption receiver capable of receiving at least one auto-route optionassociated with the authorized caller from the access table; and anincoming call terminator capable of terminating the incoming call inaccordance with the at least one auto-route option associated with theauthorized caller from the access table, wherein the at least oneauto-route option associated with the authorized caller from the accesstable further comprises at least one secondary auto-route option. 25.The method of claim 18 wherein call management is performed in awireless environment.
 26. The method of claim 18 wherein call managementis performed in a public switched telephone environment.
 27. A methodfor implementing call management comprising: receiving an incoming callfrom a caller; receiving incoming call information (ICI), wherein theICI comprises a caller identification (CI); extracting the CI from theICI; receiving subscriber provisioning information (SPI); and routingthe incoming call in accordance with the SPI, wherein routing theincoming call comprises at least one of: interactive routing; andautomatic routing, wherein automatic routing comprises: receiving anaccess table from the SPI; validating the caller as an authorized callerin the access table in accordance with the CI; receiving from the accesstable an at least one auto-route option associated with the authorizedcaller; and connecting the incoming call in accordance with at least oneauto-route option associated with the authorized caller, wherein the atleast one auto-route option associated with the authorized callercomprises at least two auto-route options for establishing a multicastroute.
 28. The method of claim 18, wherein receiving subscriberprovisioning information (SPI) includes receiving the subscriberprovisioning information having at least one secondary auto-routeoption.